This is nifty - anybody seen examples of writing a server-side view layer with this?
Manifest: A 1-file micro-back end
11–20 of 49 posts
Re: Manifest: A 1-file micro-back end
#12I'd love to see a frontend for this. Most CMSs are either tailored specifically for blogs or are complicated to set up. I've often wanted something like I guess Access or Filemaker Pro (if anyone remembers that) but with a modern UI and database. Not for production use, mind you, just like, say I have a library of books or blu-rays and want to create a catalogue of them (with images, so a spreadsheet is a no-go). Bei…
Looks like there is an admin panel demo, but can't find the login/password
Re: Manifest: A 1-file micro-back end
#13Earlier quoted context omitted.
This was also my first thought, in perhaps more confused language than snarky, though.
Um, "snarky"? How do I ask "is this last element optional, and does it have to be an emoji?" without snark? And it's the most egregious (in the "glaring" sense, not "outlandishly awful") things about the example, you don't often see emojis being a part config/programming languages outside of embedded strings, everything else is pretty self-explanatory dialect of YAML. The use of emojis looks quite similar to the way…
> SINGLE_EMOJI_COMMENT
Bwahahaha. Sorry, I’ve just imagined the poor sod who has to implement this grammar and has to decide whether presentation selectors or (potentially unknown) ZWJ sequences or (potentially unknown) letter-pairs denoting flags count parts of as single emoji (in theory they do[1], but good luck figuring out what tables you need).
> the way parameter/argument labels are introduced in Swift: in the function signature, you use two names (separated by a space) before the colon, instead of one
Side note: Swift’s style likely comes from Objective-C, which in turn comes from Smalltalk.
Re: Manifest: A 1-file micro-back end
#14Earlier quoted context omitted.
This was also my first thought, in perhaps more confused language than snarky, though.
Um, "snarky"? How do I ask "is this last element optional, and does it have to be an emoji?" without snark? And it's the most egregious (in the "glaring" sense, not "outlandishly awful") things about the example, you don't often see emojis being a part config/programming languages outside of embedded strings, everything else is pretty self-explanatory dialect of YAML. The use of emojis looks quite similar to the way…
> 2) a tad too difficult to enter unless you're on a mobile keyboard
Windows and macOS both have great on-screen keyboards (OSK)/input method editor (IME) for emoji. Many (most?) Linux desktop environments also provide one. On Windows it is Win+. or Win+; and on macOS it is Ctrl+Cmd+Space and on Gnome it is Ctrl+Shift+E,Space or Super+E.
Re: Manifest: A 1-file micro-back end
#15For a 1-file micro-backend this sure does have a lot of files and dependencies.
Re: Manifest: A 1-file micro-back end
#16I'd love to see a frontend for this. Most CMSs are either tailored specifically for blogs or are complicated to set up. I've often wanted something like I guess Access or Filemaker Pro (if anyone remembers that) but with a modern UI and database. Not for production use, mind you, just like, say I have a library of books or blu-rays and want to create a catalogue of them (with images, so a spreadsheet is a no-go). Bei…
Looks like there is an admin panel demo, but can't find the login/password
For the first example I had the same issue, but when I tried on another example it auto-populated the correct credentials.
Re: Manifest: A 1-file micro-back end
#17Has anyone tested if this works on Cloudflare pages/workers?
Just interested as I like the ease of use and free entry level, especially for small projects.
Also: interesting idea, will have a look at it some time.
Re: Manifest: A 1-file micro-back end
#18Do I have to use emojis when introducing the entities? Are they used for anything?
it appears not: https://github.com/mnfst/manifest/blob/master/packages/core/...
It would be nice if the point of the emoji was explained anywhere in the docs but I couldn't find it anywhere
Re: Manifest: A 1-file micro-back end
#19Earlier quoted context omitted.
Um, "snarky"? How do I ask "is this last element optional, and does it have to be an emoji?" without snark? And it's the most egregious (in the "glaring" sense, not "outlandishly awful") things about the example, you don't often see emojis being a part config/programming languages outside of embedded strings, everything else is pretty self-explanatory dialect of YAML. The use of emojis looks quite similar to the way…
> 2) a tad too difficult to enter unless you're on a mobile keyboard Windows and macOS both have great on-screen keyboards (OSK)/input method editor (IME) for emoji. Many (most?) Linux desktop environments also provide one. On Windows it is Win+. or Win+; and on macOS it is Ctrl+Cmd+Space and on Gnome it is Ctrl+Shift+E,Space or Super+E.
NixOS, GNOME 47, Firefox, Ctrl+Shift+E opens devtools, Super+E does nothing. I have a flatpak app called "Smile" for entering emojis which always starts up very slowly - faster to open some webchat client and copy from its emoji picker...
Re: Manifest: A 1-file micro-back end
#20The lack of object level permissions is a really spectacular footgun and the fact that it's not even on the roadmap is concerning.
Want to allow users to set their own name? I hope you're OK with any user being able to update any field of any other user too!
Added a new entry and didn't specify a policy for every single available action? They default to unauthenticated access!
> If no policy is specified for a rule, the access is public for the related action, thus anyone can manage records.
Aaaaaa!