Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

develop #2

Draft
wants to merge 17 commits into
base: main
Choose a base branch
from
Draft

develop #2

wants to merge 17 commits into from

Conversation

dch
Copy link
Contributor

@dch dch commented Apr 28, 2021

the develop branch exists so I can force-push and not feel guilty

While not required from Sofa viewpoint as the keys are converted to/from strings during marshalling,
this allows Ecto changesets to work transparently. They do not like mixed atoms & strings for keys.
dch added 5 commits May 6, 2021 11:24
- check that couchdb hashes plaintext passwords and strips out the
  password field before returning
- ensure that `type: :user` field is present
- check that PUTting new users handles multiple roles correctly
If a top-level key named "type": "Foo" is present, check to see if a
corresponding atom named :"Elixir.Foo" is present in the existing
atom table.

This permits user functions to dispatch based on atom type in the
returned doc struct, to an Ecto schema function directly, or similar
custom user function as required.

- upgrade from_map/1 and to_map/1
- add coerce_to_elixir_type/1
- add coerce_to_json_string/1
- remove struct related names from type fields
- sprinkle a few tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants