Fix naming

This commit is contained in:
Stephan Hoyer 2022-03-02 07:31:34 +01:00
parent 1c07143be4
commit 9906e23118
11 changed files with 13 additions and 13 deletions

2
.github/CODEOWNERS vendored
View file

@ -1 +1 @@
* @isiahmeadows @StephanHoyer * @dead-claudia @StephanHoyer

View file

@ -3,7 +3,7 @@ name: "\U0001F41B Bug"
about: Report a bug in Mithril.js about: Report a bug in Mithril.js
title: '' title: ''
labels: 'Type: Bug' labels: 'Type: Bug'
assignees: isiahmeadows assignees: dead-claudia
--- ---

View file

@ -3,7 +3,7 @@ name: "\U0001F680 Feature or Enhancement"
about: Suggest an idea or feature for Mithril.js about: Suggest an idea or feature for Mithril.js
title: '' title: ''
labels: 'Type: Enhancement' labels: 'Type: Enhancement'
assignees: isiahmeadows assignees: dead-claudia
--- ---

View file

@ -92,7 +92,7 @@ deploy:
# Skip until I can figure out what's going on with docs + version deployment # Skip until I can figure out what's going on with docs + version deployment
# - provider: npm # - provider: npm
# skip_cleanup: true # skip_cleanup: true
# email: me@isiahmeadows.com # email: contact@claudiameadows.dev
# api_key: # api_key:
# secure: "uPLbeJTalA/b38srb1VuWnD3eOgeKTkXf8VVUasUXIqc2xub4DSkFm1IVKSVd/rzP7EeO7+gRUs2UteNKlpZJl226IS5mFPSVtC7ViW46WSpYT0wlMsc7hrubMBGTx3/XYpPwtmMlTIGs5ICT7YkGAuju/6i79LDAB+gbnEY8Bc=" # secure: "uPLbeJTalA/b38srb1VuWnD3eOgeKTkXf8VVUasUXIqc2xub4DSkFm1IVKSVd/rzP7EeO7+gRUs2UteNKlpZJl226IS5mFPSVtC7ViW46WSpYT0wlMsc7hrubMBGTx3/XYpPwtmMlTIGs5ICT7YkGAuju/6i79LDAB+gbnEY8Bc="
# on: # on:

View file

@ -59,7 +59,7 @@ further defined and clarified by project maintainers.
## Enforcement ## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [contact@isiahmeadows.com](mailto:contact@isiahmeadows.com?subject=Mithril%20Code%20of%20Conduct). All reported by contacting the project team at [contact@claudiameadows.dev](mailto:contact@claudiameadows.dev?subject=Mithril%20Code%20of%20Conduct). All
complaints will be reviewed and investigated and will result in a response that complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident. obligated to maintain confidentiality with regard to the reporter of an incident.

View file

@ -9,7 +9,7 @@ Mithril.js was originally written by Leo Horie, but it is where it is today than
Special thanks to: Special thanks to:
- Pat Cavit, who exposed most of the public API for Mithril.js 1.0, brought in test coverage and automated the publishing process - Pat Cavit, who exposed most of the public API for Mithril.js 1.0, brought in test coverage and automated the publishing process
- Isiah Meadows, who brought in linting, modernized the test suite and has been a strong voice in design discussions - Claudia Meadows, who brought in linting, modernized the test suite and has been a strong voice in design discussions
- Zoli Kahan, who replaced the original Promise implementation with one that actually worked properly - Zoli Kahan, who replaced the original Promise implementation with one that actually worked properly
- Alec Embke, who single-handedly wrote the JSON-P implementation - Alec Embke, who single-handedly wrote the JSON-P implementation
- Barney Carroll, who suggested many great ideas and relentlessly pushed Mithril.js to the limit to uncover design issues prior to Mithril.js 1.0 - Barney Carroll, who suggested many great ideas and relentlessly pushed Mithril.js to the limit to uncover design issues prior to Mithril.js 1.0

View file

@ -267,7 +267,7 @@ JSX and hyperscript are two different syntaxes you can use for specifying vnodes
- Hyperscript is more approachable if you come from a backend JS background that doesn't involve much HTML or XML. It's more concise with less redundancy, and it provides a CSS-like sugar for static classes, IDs, and other attributes. It also can be used with no build step at all, although [you can add one if you wish](https://github.com/MithrilJS/mopt). And it's slightly easier to work with in the face of a lot of dynamic content, because you don't need to "interpolate" anything. However, the terseness does make it harder to read for some people, especially those less experienced and coming from a front end HTML/CSS/XML background, and I'm not aware of any plugins that auto-complete parts of hyperscript selectors like IDs, classes, and attributes. - Hyperscript is more approachable if you come from a backend JS background that doesn't involve much HTML or XML. It's more concise with less redundancy, and it provides a CSS-like sugar for static classes, IDs, and other attributes. It also can be used with no build step at all, although [you can add one if you wish](https://github.com/MithrilJS/mopt). And it's slightly easier to work with in the face of a lot of dynamic content, because you don't need to "interpolate" anything. However, the terseness does make it harder to read for some people, especially those less experienced and coming from a front end HTML/CSS/XML background, and I'm not aware of any plugins that auto-complete parts of hyperscript selectors like IDs, classes, and attributes.
You can see the tradeoffs come into play in more complex trees. For instance, consider this hyperscript tree, adapted from a real-world project by [@isiahmeadows](https://github.com/isiahmeadows/) with some alterations for clarity and readability: You can see the tradeoffs come into play in more complex trees. For instance, consider this hyperscript tree, adapted from a real-world project by [@dead-claudia](https://github.com/dead-claudia) with some alterations for clarity and readability:
```javascript ```javascript
function SummaryView() { function SummaryView() {

View file

@ -879,7 +879,7 @@ Since v2.x uses standards-compliant Promises, `m.sync` is redundant. Use `Promis
```javascript ```javascript
m.sync([ m.sync([
m.request({ method: 'GET', url: 'https://api.github.com/users/lhorie' }), m.request({ method: 'GET', url: 'https://api.github.com/users/lhorie' }),
m.request({ method: 'GET', url: 'https://api.github.com/users/isiahmeadows' }), m.request({ method: 'GET', url: 'https://api.github.com/users/dead-claudia' }),
]) ])
.then(function (users) { .then(function (users) {
console.log("Contributors:", users[0].name, "and", users[1].name) console.log("Contributors:", users[0].name, "and", users[1].name)
@ -891,7 +891,7 @@ m.sync([
```javascript ```javascript
Promise.all([ Promise.all([
m.request({ method: 'GET', url: 'https://api.github.com/users/lhorie' }), m.request({ method: 'GET', url: 'https://api.github.com/users/lhorie' }),
m.request({ method: 'GET', url: 'https://api.github.com/users/isiahmeadows' }), m.request({ method: 'GET', url: 'https://api.github.com/users/dead-claudia' }),
]) ])
.then(function (users) { .then(function (users) {
console.log("Contributors:", users[0].name, "and", users[1].name) console.log("Contributors:", users[0].name, "and", users[1].name)

View file

@ -29,7 +29,7 @@ _2019-02-07_
- ospec: Test results now include `.message` and `.context` regardless of whether the test passed or failed. (#2227 @robertakarobin) - ospec: Test results now include `.message` and `.context` regardless of whether the test passed or failed. (#2227 @robertakarobin)
<!-- Add new lines here. Version number will be decided later --> <!-- Add new lines here. Version number will be decided later -->
- Add `spy.calls` array property to get the `this` and `arguments` values for any arbitrary call. (#2221 @isiahmeadows) - Add `spy.calls` array property to get the `this` and `arguments` values for any arbitrary call. (#2221 [@dead-claudia](https://github.com/dead-claudia))
- Added `.throws` and `.notThrows` assertions to ospec. (#2255 @robertakarobin) - Added `.throws` and `.notThrows` assertions to ospec. (#2255 @robertakarobin)
- Update `glob` dependency. - Update `glob` dependency.

View file

@ -531,7 +531,7 @@ o.spec("attributes", function() {
This incomplete test is meant for testing #1916. This incomplete test is meant for testing #1916.
However it cannot be completed until #1978 is addressed However it cannot be completed until #1978 is addressed
which is a lack a working select.selected / option.selected which is a lack a working select.selected / option.selected
attribute. Ask isiahmeadows. attribute. Ask @dead-claudia.
o("render select options", function() { o("render select options", function() {
var select = m("select", {selectedIndex: 0}, var select = m("select", {selectedIndex: 0},

View file

@ -197,7 +197,7 @@ of contents accordingly.
// deploy: // deploy:
// - provider: npm // - provider: npm
// skip_cleanup: true // skip_cleanup: true
// email: 'contact@isiahmeadows.com' // email: 'contact@claudiameadows.dev'
// api_key: // api_key:
// secure: 'output of `travis encrypt NPM_AUTH_TOKEN`' // secure: 'output of `travis encrypt NPM_AUTH_TOKEN`'
// on: // on:
@ -206,7 +206,7 @@ of contents accordingly.
// - provider: npm // - provider: npm
// skip_cleanup: true // skip_cleanup: true
// tag: next // tag: next
// email: 'contact@isiahmeadows.com' // email: 'contact@claudiameadows.dev'
// api_key: // api_key:
// secure: 'output of `travis encrypt NPM_AUTH_TOKEN`' // secure: 'output of `travis encrypt NPM_AUTH_TOKEN`'
// on: // on: