apitech/jitsi-meet - jitsi-meet - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Дамян Минков	389d455daa	feat: Passing the url to conference mapper (#11013 ) * fix: Moves getDialInConferenceID, so we can reuse conf mapper url generation. * fix: Moves getDialInNumbers, so we can reuse url generation. * squash: Moves dialInInfo page path to constants. * feat: Adds the location address as a param to the conf mapper request. * feat: Adds option conf mapper and numbers urls to contain parameters (?). * squash: Adds more doc comments. * squash: Makes sure we strip url params if any, and they do not reach fetch.	4 years ago
Tudor-Ovidiu Avram	b889bd5664	fix(jaas) replace only the first slash in a pathname	5 years ago
Tudor-Ovidiu Avram	0f64c66f91	fix(jaas) fix double slash for branded invite urls	5 years ago
Tudor-Ovidiu Avram	8a4fb72eae	feat(branding) allow invite links to be branded	6 years ago
paweldomas	7684b2bf98	ref: move getCurrentConferenceUrl to base/connection Moves getCurrentConferenceUrl method to base/connection to allow reuse. The new location is not ideal, but looks the best based on the imports required (trying to avoid circular dependencies).	7 years ago
paweldomas	e4af5ddbe9	feat(base/connection): throw error and add isInviteURLReady	7 years ago
Bettenbuk Zoltan	18d908ce84	Fix flow errors from base/connection	7 years ago
Bettenbuk Zoltan	3fdf944763	Fix eslint/jsdoc warnings (doc change only!)	7 years ago
Zoltan Bettenbuk	cc6e04ddf8	[RN] Fix calendar alerts when case sensitive URLs are used	8 years ago
Lyubo Marinov	4bf19d73fd	[RN] Fix documentation comments * Javadoc introduced @code as a replacement of <code> and <tt> which is better aligned with other javadoc tags such as @link. Use it in the Java source code. If we switch to Kotlin, then we'll definitely use Markdown. * There are more uses of @code in the JavaScript source code than <tt> so use @code for the sake of consistency. Eventually, I'd rather we switch to Markdown because it's easier on my eyes. * Xcode is plain confused by @code and @link. The Internet says that Xcode supports the backquote character to denote the beginning and end of a string of characters which should be formatted for display as code but it doesn't work for me. <tt> is not rendered at all. So use the backquote which is rendered itself. Hopefully, if we switch to Markdown, then it'll be common between JavaScript and Objective-C source code.	8 years ago
Lyubo Marinov	241dc3b147	[RN] Support XMPP authentication	8 years ago
paweldomas	141acea194	[RN] Support XMPP authentication	8 years ago
Lyubo Marinov	6545a7a1bb	Remove duplication	9 years ago
Lyubo Marinov	377be4272a	[RN] Fix the conference URL delivered to JitsiMeetView's listeners	9 years ago
Lyubo Marinov	1748049322	[RN] Remove unncessary characters from the invite URL	9 years ago
Lyubo Marinov	a4a13bed84	Invite URL w/o (hash & query/search) params	9 years ago
Lyubo Marinov	ec454d1da0	Move ConferenceUrl.inviteURL into React and redux	9 years ago
Lyubo Marinov	2f3706bd37	[RN] Simplify There were getDomain, setDomain, SET_DOMAIN, setRoomURL, SET_ROOM_URL which together were repeating one and the same information and in the case of the 'room URL' abstraction was not 100% accurate because it would exist even when there was no room. Replace them all with a 'location URL' abstraction which exists with or without a room. Then the 'room URL' abstraction was not used in (mobile) feature share-room. Use the 'location URL' there now. Finally, removes source code duplication in supporting the Web application context root.	9 years ago
Lyubo Marinov	f50a31b4e8	[RN] Simplify the source code	9 years ago
Lyubomir Marinov	b50f858556	[flow] Expand the coverage of flow-monitored files	9 years ago
Lyubomir Marinov	d55e0f70d9	Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at `2f23d98424` i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.	9 years ago