This is not a legal document, members should follow the spirit of this code. Everybody makes mistakes, but second chances do not have priority over others’ comfort.
Conduct
Please be kind, courteous, and friendly. There’s no need to be mean or rude.
Please communicate in public. This is a public community, and conversations should happen in the main server unless the matter under discussion is sensitive or otherwise private.
Please read the room. This is a large community with many different humans. Before posting in a channel with hundreds of members, we ask that you take the time to read the room.
Please use gender neutral language. If somebody requests you use a pronoun, please respect their wishes.
Please respect that people have differences of opinion. Every design or implementation choice carries a trade-off and numerous costs. There is seldom a single right answer.
Please keep unstructured critique to a minimum. Address the main topic at hand before pursuing a tangent.
Please use a display name that represents you. Names that detract from a friendly, safe and welcoming environment for all will be addressed.
Any form of unacceptable behavior will not be tolerated. You will be excluded from interaction if you insult, demean, or harass anyone. In particular, behavior that excludes people in socially marginalized groups will not be tolerated. We interpret the term “unacceptable behavior” as the definition in the Citizen Code of Conduct (https://github.com/stumpsyn/policies/blob/master/citizen_code_of_conduct.md#4-unacceptable-behavior).
Likewise any destructive or attention-stealing behavior is not welcome.
Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the staff. Whether you’re a regular contributor or a newcomer, we care about making this community a safe place for you and we’ve got your back.
If someone takes issue with something you said or did, resist the urge to be defensive. Stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better. We are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as you earn their trust.
Adapted from the Reactiflux code of conduct (https://reactiflux.com/conduct), which is itself adapted from the Rust code of conduct (https://www.rust-lang.org/policies/code-of-conduct).
Hi, we wanted to share an update with you all.
In the past, you’ve asked for increased customization of Cord components, and we’ve told you that we were working on something.
Well, today is the day, we’d like to share the beta of our v2 components (Thread, Message, Composer, Avatar, and constituent components) that allow for replacement.
With these new components, you can get all the behavior that you normally get but swap out any particular piece for your own component. Don’t like our Avatar hover behavior, add your own. Want to add a custom menu item to Threads, go ahead. Want the composer to brew a cup of coffee on every key press, totally doable. This is designed to increase flexibility for you to build the app you want to build. Additionally, these components now all render in your React tree without going through web components so you should no longer see things rerender on different React cycles. We are really excited about what can be done with this, and we’d love your feedback on it. We are super happy to discuss it here on https://community.cord.com. We want to make sure that what we have built really does give you the functionality and flexibility you’ve asked for.
To use this, you’ll need to install the Cord SDK at version 1.42.1 (or later). Docs for the new components are available https://docs.cord.com/components?version=2.0 .
There is more documentation at https://docs.cord.com/customization/custom-react-components about the capabilities, and a working example that shows how to turn our thread into one like github (https://docs.cord.com/customization/custom-react-components/tutorial).
Previously, location filters in some places, such as the /v1/threads REST API, defaulted to being exact match, and in others they defaulted to being partial match. We've changed so that location filters default to exact matching everywhere. If you want partial matching behavior, be sure to pass your filter as { value: yourLocationFilter, partialMatch: true }.