apitech
/
Rocket.Chat
mirror of https://github.com/RocketChat/Rocket.Chat
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
The communications platform that puts data protection first.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
29516 Commits
965 Branches
1252 Tags
2.2 GiB
 
 
 
 
 
Tag: Branch: Tree: develop
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'develop'
${ noResults }
Rocket.Chat/apps/meteor/client
History
Kevin Aleman 3c47215f47
feat: Virtru as attribute store (#40634) 		1 day ago
..
apps chore: migrate DDP callers to REST endpoints (used methods with REST replacement) (#40659) 1 week ago
cachedStores fix: `abacAttributes` reactivity (#40499) 3 weeks ago
components revert: Phishing resistant multi factor authentication (#40679) 1 week ago
contexts feat(apps): Migrate app management code from @rocket.chat/apps-engine to @rocket.chat/apps internal package (#40343) 4 weeks ago
definitions refactor: incrementally remove Meteor deps from the frontend (#40268) 1 month ago
hooks chore: migrate DDP callers to REST endpoints (used methods with REST replacement) (#40659) 1 week ago
lib revert: Phishing resistant multi factor authentication (#40679) 1 week ago
meteor refactor(client): drop misc Meteor type/value imports from 2FA + startup (#40556) 2 weeks ago
navbar chore: migrate DDP callers to REST endpoints (used methods with REST replacement) (#40659) 1 week ago
portals refactor: Move `TooltipProvider` to `ui-client` package, reimplement document references and deduplicate portals (#40392) 1 month ago
providers refactor(core-typings): Record types missing a required `_updatedAt` field (#38528) 2 weeks ago
router refactor(client): centralize __meteor_runtime_config__ access (#40487) 3 weeks ago
sidebar chore(room): speed up room open by parallelizing fetches and caching (#40718) 1 week ago
startup revert: Phishing resistant multi factor authentication (#40679) 1 week ago
stores fix: Remove the delay of waiting on event on WS to consider a message sent (#38067) 5 months ago
stories refactor(client): remove legacy streamerCentral, migrate user-presence to sdk.onAnyStreamEvent (#40542) 2 weeks ago
uikit/hooks feat(uikit): add room to some other interaction contexts (#39858) 3 weeks ago
views feat: Virtru as attribute store (#40634) 1 day ago
README.md
…
importPackages.ts refactor(client): remove legacy streamerCentral, migrate user-presence to sdk.onAnyStreamEvent (#40542) 2 weeks ago
main.ts chore(@rocket.chat/ddp-client): introduce experimental Meteor independent DDP client (re-add) (#40430) 4 weeks ago
serviceWorker.ts
…
ui.ts feat(a11y): Bring keyboard shortcuts to a global context (#40169) 2 months ago

README.md

How does the folder structure work in the frontend?

The folder structure should follow rocketchat's html 'semantics' like:

    main   -> room
                -> header
                    ...
                -> contextualbar
                    roominfo
                        ...
            -> sidebar
                -> Header
                    -> search
                    -> actions
                        ...
                -> list
                    ...
                -> footer
                    ...

Each folder is composed by:

File
index.jsx
ContainerComponent.jsx
contexts (optional)
providers (optional)
components (optional)
hooks (optional)
libs (optional)

We strongly suggest that you start developing your components/hooks/libs inside the folder where they will be directly used. If you ever find that you will use them in more than one place, then you should "promote" the code to an upper level, where it can be commonly accessed by all others

we have being moving code from blaze to react, but sometimes we will need render under blaze enviroment, to do that use createTemplateForComponent