| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the return_url was hardcoded for all environments.
It would create an issue where authentication outside of development
would redirect to the wrong site.
With the previous commit we introduced a staging environment and
an environment-specific configuration file allowing to hardcode
return_url for each environment.
This commit fixes the proper capture of the SSO secret in the
current configuration and introduces an SSO::MissingSecretError
class that is raised when there's no configured secret.
https://gitlab.com/incommon.cc/incommon-map/-/issues/1
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
Since we must associate other models (e.g., classifications) to a Resource,
we use a composite model to save all changes inside a database transaction.
This approach makes it simpler to handle resources and their associations.
Work remains to fix the geolocation and reverse geolocation to ensure
these are in sync.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The UUIDResolver adds a route at `/by-uuid/:uuid` that enables
applications to request information about a given UUID.
The UUID must be a Random UUID (version 4, see RFC 4122).
If an invalid UUID is given, the controller will return 422 Unprocessable Entity.
If a valid UUID is given:
- 404 indicates that the UUID is not assigned to anything known to the system.
- 302 indicates that the UUID was assigned to a record, and the User-Agent
will be redirected to that record's Location as indicated in the response header.
- 200 indicates that the UUID was assigned to more than one record (which is unlikely)
and will list those records.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
The server changed, and so did the link to the IN COMMON logo.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
To some it may be more straightforward to think of the members of
an Agent as "users". This commit accepts using `Agent#users` instead
of `Agent#members`, but warns developers that they should be using
the other method.
Since Agent has_many Users, the Principle of Least Surprise warrants
that `agent.users` does something.
But they're really members.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Ensure new users belong to an Agent
Users may come without the correct group information, leading
to a situation where they have no Agent assigned to them.
The application cannot handle this, so we ensure new users
are at least associated to the new Anonymous Agent.
2. Introduce a default avatar
Users coming without an avatar would see a broken view.
Now they're assigned a default avatar, which shows the IN COMMON
icon logo instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Since we moved away from Roles it's important to maintain a
default Agent that is distinct from the previous default
IN COMMON Agent.
Previously, a user without a proper group would be granted the
`observer` role in the default Agent, enough to create new
resources.
Now, we consider anonymous users to be part of the Anonymous
Agent, which also brings the possibility for them to edit yet
to be accepted Resources.
|
| |
|
|
|
|
|
|
|
|
|
| |
This Leaflet plugin adds a live address search on the map.
We anticipate the possibility to find POIs from their address,
or to check whether an address is already in the database.
For now it enables looking up an address.
https://smeijer.github.io/leaflet-geosearch/leaflet-control/
|
| |
|
|
|
|
|
|
| |
Using `leaflet-easyprint`, we can add a button to print a current view of the map.
This commit adds the functionality, without customization.
Source: https://github.com/rowanwins/leaflet-easyPrint
|
| | |
|
| |
|
|
|
| |
Since we moved CSS to Webpack, also tell that to
the asset pipeline.
|
| |
|
|
| |
Cleaning up the code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Using both the asset pipeline and webpack is confusing
and leads to unpredictable results in production.
This commit moves all (S)CSS to Webpack under `app/javascript/scss`
so that we can test whether the development interface results
in a consistent production deployment.
In order to load the ForkAwesome fonts we used a long path:
`$fa-font-path: "../../../node_modules/fork-awesome/fonts";`
Not sure whether this works...
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Make category style independent of database ID to prevent
bad surprises between development and production. Instead
we use the rank.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
- Replace MakiMarkers with ExtraMarkers and ForkAwesome
- Add HTML popup binding
|
| | |
|
| |
|
|
| |
Original colors are kept as comments for future reference.
|
| | |
|
| | |
|
| | |
|
